Skip to content

Conversation

@sharmagot
Copy link
Collaborator

This MR enhances the client_os value reported by the Vertica Node.js driver in session information.
Instead of returning generic values such as linux or win32, the driver now reports a detailed and meaningful OS string, consistent with other Vertica client drivers (vertica-python, ODBC, JDBC).

Problem Statement

Currently, when connecting using vertica-nodejs, the client_os field contains only basic OS identifiers.
Customers expect richer OS information in v_monitor.sessions, similar to what is provided by other supported drivers.

Solution

Updated client_os to include OS type, release, and architecture.
Added robust fallback handling:
Falls back to os.platform() if detailed OS retrieval fails.
Uses "unknown" if all OS lookups fail.
Ensured output consistency with other Vertica client drivers.

Changes Included

connection-parameters.js
Enhanced client_os construction with detailed OS information and fallback logic.
Integration test update
Updated expectations to validate the new client_os format.
New unit tests
Added coverage for:
Detailed OS reporting
Fallback to os.platform()
Final fallback to "unknown"
os_issue_fix

@sharmagot sharmagot self-assigned this Jan 12, 2026
@CLAassistant
Copy link

CLAassistant commented Jan 12, 2026

CLA assistant check
All committers have signed the CLA.

@h-serizawa
Copy link

@sharmagot, Can you also review the MR of #155?

@sharmagot sharmagot requested a review from sivaalamp January 13, 2026 12:04
@sharmagot
Copy link
Collaborator Author

@sharmagot, Can you also review the MR of #155?
Hi h-serizawa,
Yes, I have seen your code changes. They are almost the same; I have added some additional test cases on top of them. I will also work on fixing the pipeline failures, as I’ve noticed there hasn’t been a successful pipeline run for a long time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants